Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-221801 | OL07-00-030610 | SV-221801r853707_rule | Medium |
Description |
---|
Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Satisfies: SRG-OS-000392-GPOS-00172, SRG-OS-000470-GPOS-00214, SRG-OS-000473-GPOS-00218 |
STIG | Date |
---|---|
Oracle Linux 7 Security Technical Implementation Guide | 2023-03-06 |
Check Text ( C-23516r419475_chk ) |
---|
Verify the operating system generates audit records when unsuccessful account access events occur. Check the file system rule in "/etc/audit/audit.rules" with the following commands: # grep -i /var/run/faillock /etc/audit/audit.rules -w /var/run/faillock -p wa -k logins If the command does not return any output, this is a finding. |
Fix Text (F-23505r419476_fix) |
---|
Configure the operating system to generate audit records when unsuccessful account access events occur. Add or update the following rule in "/etc/audit/rules.d/audit.rules": -w /var/run/faillock -p wa -k logins The audit daemon must be restarted for the changes to take effect. |